Device, method, and graphical user interface for managing user interface content and user interface elements by dynamic snapping of user interface elements to alignment guides

ABSTRACT

Alignment guides configured for adaptive snap-to behavior are disclosed. In one embodiment, during a user interface element resize or move gesture, match-priority values for potential alignment guides are determined based at least on gravity values associated with said alignment guides. After a displayed object is snapped to a first alignment guide having the highest match-priority value, and the user interface element is moved away from the first alignment guide during the resize or move gesture, the gravity value associated with the first alignment guide is adjusted.

TECHNICAL FIELD

The disclosed embodiments relate generally to computing devices, and more particularly, to computing devices and methods for managing user interface content and user interface elements.

BACKGROUND

The use of computers and other electronic computing devices to manage user interface content and user interface elements has increased significantly in recent years. Exemplary computing devices that include capabilities of managing user interface content and user interface elements include mobile telephones, desktop computers, laptop computers, tablet computers, electronic book readers, consumer electronics, personal digital assistants, etc.

Many users rely on electronic computing devices for managing user interface content and user interface elements. Unfortunately, existing methods for managing user interface content and user interface elements are cumbersome and inefficient. In addition, existing methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.

Accordingly, there is a need for computing devices with faster, more efficient methods and interfaces for managing user interface content and user interface elements, such as using alignment guides configured for adaptive snap-to behavior during user interface element movement and resize gestures. Such methods and interfaces may complement or replace conventional methods for managing user interface content and user interface elements. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

SUMMARY

The above deficiencies and other problems associated with user interfaces for computing devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions may include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital video recording, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions may be included in a computer readable storage medium or other computer program product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at a computing device with a display and one or more user input devices adapted to detect user gestures. The method includes displaying a user interface including: at least one user interface element configured to be moved within the user interface in response to user gestures and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved. The method also includes detecting a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, initiating movement of the user interface element within the user interface; after movement of the user interface element is initiated, snapping the user interface element to a first alignment guide; after snapping the user interface element to the first alignment guide, detecting a second portion of the first user gesture that is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: moving the user interface element away from the first alignment guide, and, adjusting the gravity variable associated with the first alignment guide. After adjusting the gravity variable associated with the first alignment guide, the method includes detecting a third portion of the first user gesture; in response to detecting the third portion of the first user gesture, snapping the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide.

In accordance with some embodiments, a computing device includes a display, one or more user input devices adapted to detect user gestures, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for displaying a user interface including: at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein: respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved. The one or more programs also include instructions for detecting a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, initiating movement of the user interface element within the user interface; after movement of the user interface element is initiated, snapping the user interface element to a first alignment guide; after snapping the user interface element to the first alignment guide, detecting a second portion of the first user gesture that is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: moving the user interface element away from the first alignment guide, and, adjusting the gravity variable associated with the first alignment guide; after adjusting the gravity variable associated with the first alignment guide: detecting a third portion of the first user gesture; in response to detecting the third portion of the first user gesture, snapping the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide.

In accordance with some embodiments there is a graphical user interface on a computing device with a display, one or more user input devices adapted to detect user gestures, a memory, and one or more processors to execute one or more programs stored in the memory. The graphical user interface includes a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved; wherein a first portion of a first user gesture is detected, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, movement of the user interface element is initiated within the user interface; after movement of the user interface element is initiated, the user interface element is snapped to a first alignment guide; after snapping the user interface element to the first alignment guide, a second portion of the first user gesture is detected, wherein the second portion of the first user gesture is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: the user interface element is moved away from the first alignment guide, and, the gravity variable associated with the first alignment guide is adjusted; after adjusting the gravity variable associated with the first alignment guide: a third portion of the first user gesture is detected; in response to detecting the third portion of the first user gesture, the user interface element is snapped to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide.

In accordance with some embodiments, a computer readable storage medium has stored therein one or more programs, the one or more programs comprising instructions, which when executed by a computing device with a display and one or more user input devices adapted to detect user gestures, cause the computing device to display a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein: respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved. The one or more programs also comprise instructions to detect a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, initiate movement of the user interface element within the user interface; after movement of the user interface element is initiated, snap the user interface element to a first alignment guide; after snapping the user interface element to the first alignment guide, detect a second portion of the first user gesture that is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: move the user interface element away from the first alignment guide, and, adjust the gravity variable associated with the first alignment guide; after adjusting the gravity variable associated with the first alignment guide: detect a third portion of the first user gesture; in response to detecting the third portion of the first user gesture, snap the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide.

In accordance with some embodiments, a computing device includes a display; one or more user input devices adapted to detect user gestures; and means for displaying a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved; means for detecting a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, means for initiating movement of the user interface element within the user interface; after movement of the user interface element is initiated, means for snapping the user interface element to a first alignment guide; after snapping the user interface element to the first alignment guide, means for detecting a second portion of the first user gesture that is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: means for moving the user interface element away from the first alignment guide, and, means for adjusting the gravity variable associated with the first alignment guide; after adjusting the gravity variable associated with the first alignment guide: means for detecting a third portion of the first user gesture; in response to detecting the third portion of the first user gesture, means for snapping the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide.

In accordance with some embodiments, an information processing apparatus for use in a computing device includes a display, one or more user input devices adapted to detect user gestures, and means for displaying a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved; means for detecting a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, means for initiating movement of the user interface element within the user interface; after movement of the user interface element is initiated, means for snapping the user interface element to a first alignment guide; after snapping the user interface element to the first alignment guide, means for detecting a second portion of the first user gesture that is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: means for moving the user interface element away from the first alignment guide, and, means for adjusting the gravity variable associated with the first alignment guide; after adjusting the gravity variable associated with the first alignment guide: means for detecting a third portion of the first user gesture; in response to detecting the third portion of the first user gesture, means for snapping the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide.

In accordance with some embodiments, a method is performed at a computing device with a display and one or more user input devices adapted to detect user gestures. The method includes displaying a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved. The method also includes detecting a first portion of a user gesture, the user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the user gesture, moving the user interface element within the user interface; while the user interface element is moving within the user interface: determining respective locations within the user interface of the user interface element; when the user interface element is at respective locations of the user interface: determining respective match priority values for a plurality of alignment guides, wherein respective match priority values are based at least on respective gravity variables and a current location of the user interface element; comparing a match priority value associated with a first alignment guide in the plurality of alignment guides with a match priority value associated with a second alignment guide in the plurality of alignment guides; moving the user interface element to an alignment guide associated with a greatest determined match priority value.

In accordance with some embodiments, a computing device includes a display, one or more user input devices adapted to detect user gestures, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for displaying a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved. The one or more programs also include instructions for detecting a first portion of a user gesture, the user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the user gesture, moving the user interface element within the user interface; while the user interface element is moving within the user interface: determining respective locations within the user interface of the user interface element; when the user interface element is at respective locations of the user interface: determining respective match priority values for a plurality of alignment guides, wherein respective match priority values are based at least on respective gravity variables and a current location of the user interface element; comparing a match priority value associated with a first alignment guide in the plurality of alignment guides with a match priority value associated with a second alignment guide in the plurality of alignment guides; moving the user interface element to an alignment guide associated with a greatest determined match priority value.

In accordance with some embodiments there is a graphical user interface on a computing device with a display, one or more user input devices, a memory, and one or more processors to execute one or more programs stored in the memory. The graphical user interface includes a user interface having at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved; wherein a first portion of a user gesture is detected, the user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the user gesture, the user interface element is moved within the user interface; while the user interface element is moving within the user interface: respective locations within the user interface are determined for the user interface element; when the user interface element is at respective locations of the user interface respective match priority values are determined for a plurality of alignment guides, wherein respective match priority values are based at least on respective gravity variables and a current location of the user interface element; a match priority value associated with a first alignment guide in the plurality of alignment guides is compared with a match priority value associated with a second alignment guide in the plurality of alignment guides; the user interface element is snapped to an alignment guide associated with a greatest determined match priority value.

In accordance with some embodiments, a computer readable storage medium has stored therein one or more programs, the one or more programs comprising instructions, which when executed by a computing device with a display and one or more user input devices adapted to detect user gestures, cause the computing device to display a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved. The one or more programs also comprise instructions which cause the computing device to detect a first portion of a user gesture, the user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the user gesture, move the user interface element within the user interface; while the user interface element is moving within the user interface: determine respective locations within the user interface of the user interface element; when the user interface element is at respective locations of the user interface: determine respective match priority values for a plurality of alignment guides, wherein respective match priority values are based at least on respective gravity variables and a current location of the user interface element; compare a match priority value associated with a first alignment guide in the plurality of alignment guides with a match priority value associated with a second alignment guide in the plurality of alignment guides; move the user interface element to an alignment guide associated with a greatest determined match priority value.

In accordance with some embodiments, a computing device includes a display, one or more user input devices adapted to detect user gestures, and means for displaying a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved. The device also includes means for detecting a first portion of a user gesture, the user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the user gesture, means for moving the user interface element within the user interface; while the user interface element is moving within the user interface: means for determining respective locations within the user interface of the user interface element; when the user interface element is at respective locations of the user interface: means for determining respective match priority values for a plurality of alignment guides, wherein respective match priority values are based at least on respective gravity variables and a current location of the user interface element; means for comparing a match priority value associated with a first alignment guide in the plurality of alignment guides with a match priority value associated with a second alignment guide in the plurality of alignment guides; means for moving the user interface element to an alignment guide associated with a greatest determined match priority value.

In accordance with some embodiments, an information processing apparatus for use in a computing device includes a display, one or more user input devices adapted to detect user gestures, and means for displaying a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved. The device also includes means for detecting a first portion of a user gesture, the user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the user gesture, means for moving the user interface element within the user interface; while the user interface element is moving within the user interface: means for determining respective locations within the user interface of the user interface element; when the user interface element is at respective locations of the user interface: means for determining respective match priority values for a plurality of alignment guides, wherein respective match priority values are based at least on respective gravity variables and a current location of the user interface element; means for comparing a match priority value associated with a first alignment guide in the plurality of alignment guides with a match priority value associated with a second alignment guide in the plurality of alignment guides; means for moving the user interface element to an alignment guide associated with a greatest determined match priority value.

Thus, the computing devices disclosed herein are provided with faster, more efficient methods and interfaces for managing user interface content and user interface elements, including use of alignment guides configured for adaptive snap-to behavior during user interface element movement and resize gestures. These computing devices with faster, more efficient methods and interfaces increase user effectiveness, efficiency, and satisfaction. Such methods and interfaces may complement or replace conventional methods for manipulating user interface objects.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of the invention as well as additional embodiments thereof, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

FIGS. 1A and 1B are block diagrams illustrating portable multifunction devices with touch-sensitive displays in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu of applications on a portable multifunction device in accordance with some embodiments.

FIG. 4C illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

FIGS. 5A-5P illustrate exemplary user interfaces for manipulating user interface objects in accordance with some embodiments.

FIGS. 6A-6C are flow diagrams illustrating a method of manipulating user interface objects in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the present invention. The first contact and the second contact are both contacts, but they are not the same contact.

The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.

Embodiments of computing devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the computing device is a portable communications device such as a mobile telephone that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone® and iPod Touch® devices from Apple, Inc. of Cupertino, Calif. Other portable devices such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads) may also be used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).

In the discussion that follows, a computing device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the computing device may include one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.

The device supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

The various applications that may be executed on the device may use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device may support the variety of applications with user interfaces that are intuitive and transparent.

The user interfaces may include one or more soft keyboard embodiments. The soft keyboard embodiments may include standard (QWERTY) and/or non-standard configurations of symbols on the displayed icons of the keyboard, such as those described in U.S. patent application Ser. Nos. 11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, and 11/459,615, “Touch Screen Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, the contents of which are hereby incorporated by reference in their entirety. The keyboard embodiments may include a reduced number of icons (or soft keys) relative to the number of keys in existing physical keyboards, such as that for a typewriter. This may make it easier for users to select one or more icons in the keyboard, and thus, one or more corresponding symbols. The keyboard embodiments may be adaptive. For example, displayed icons may be modified in accordance with user actions, such as selecting one or more icons and/or one or more corresponding symbols. One or more applications on the device may utilize common and/or different keyboard embodiments. Thus, the keyboard embodiment used may be tailored to at least some of the applications. In some embodiments, one or more keyboard embodiments may be tailored to a respective user. For example, one or more keyboard embodiments may be tailored to a respective user based on a word usage history (lexicography, slang, individual usage) of the respective user. Some of the keyboard embodiments may be adjusted to reduce a probability of a user error when selecting one or more icons, and thus one or more symbols, when using the soft keyboard embodiments.

Attention is now directed towards embodiments of portable devices with touch-sensitive displays. FIGS. 1A and 1B are block diagrams illustrating portable multifunction devices 100 with touch-sensitive displays 112 in accordance with some embodiments. The touch-sensitive display 112 is sometimes called a “touch screen” for convenience, and may also be known as or called a touch-sensitive display system. The device 100 may include a memory 102 (which may include one or more computer readable storage mediums), a memory controller 122, one or more processing units (CPU's) 120, a peripherals interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and an external port 124. The device 100 may include one or more optical sensors 164. These components may communicate over one or more communication buses or signal lines 103.

It should be appreciated that the device 100 is only one example of a portable multifunction device 100, and that the device 100 may have more or fewer components than shown, may combine two or more components, or a may have a different configuration or arrangement of the components. The various components shown in FIGS. 1A and 1B may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of the device 100, such as the CPU 120 and the peripherals interface 118, may be controlled by the memory controller 122.

The peripherals interface 118 couples the input and output peripherals of the device to the CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for the device 100 and to process data.

In some embodiments, the peripherals interface 118, the CPU 120, and the memory controller 122 may be implemented on a single chip, such as a chip 104. In some other embodiments, they may be implemented on separate chips.

The RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. The RF circuitry 108 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. The RF circuitry 108 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

The audio circuitry 110, the speaker 111, and the microphone 113 provide an audio interface between a user and the device 100. The audio circuitry 110 receives audio data from the peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal to human-audible sound waves. The audio circuitry 110 also receives electrical signals converted by the microphone 113 from sound waves. The audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to the peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or the RF circuitry 108 by the peripherals interface 118. In some embodiments, the audio circuitry 110 also includes a headset jack (e.g. 212, FIG. 2). The headset jack provides an interface between the audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).

The I/O subsystem 106 couples input/output peripherals on the device 100, such as the touch screen 112 and other input/control devices 116, to the peripherals interface 118. The I/O subsystem 106 may include a display controller 156 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input/control devices 116 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) may include an up/down button for volume control of the speaker 111 and/or the microphone 113. The one or more buttons may include a push button (e.g., 206, FIG. 2). A quick press of the push button may disengage a lock of the touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to the device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

The touch-sensitive touch screen 112 provides an input interface and an output interface between the device and a user. The display controller 156 receives and/or sends electrical signals from/to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.

A touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. The touch screen 112 and the display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on the touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on the touch screen. In an exemplary embodiment, a point of contact between a touch screen 112 and the user corresponds to a finger of the user.

The touch screen 112 may use LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies may be used in other embodiments. The touch screen 112 and the display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with a touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple, Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of the touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, a touch screen 112 displays visual output from the portable device 100, whereas touch sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of the touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.

The touch screen 112 may have a resolution in excess of 100 dpi. In an exemplary embodiment, the touch screen has a resolution of approximately 160 dpi. The user may make contact with the touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which are much less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, the device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

In some embodiments, the device 100 may include a physical or virtual click wheel as an input control device 116. A user may navigate among and interact with one or more graphical objects (e.g., icons) displayed in the touch screen 112 by rotating the click wheel or by moving a point of contact with the click wheel (e.g., where the amount of movement of the point of contact is measured by its angular displacement with respect to a center point of the click wheel). The click wheel may also be used to select one or more of the displayed icons. For example, the user may press down on at least a portion of the click wheel or an associated button. User commands and navigation commands provided by the user via the click wheel may be processed by an input controller 160 as well as one or more of the modules and/or sets of instructions in memory 102. For a virtual click wheel, the click wheel and click wheel controller may be part of the touch screen 112 and the display controller 156, respectively. For a virtual click wheel, the click wheel may be either an opaque or semitransparent object that appears and disappears on the touch screen display in response to user interaction with the device. In some embodiments, a virtual click wheel is displayed on the touch screen of a portable multifunction device and operated by user contact with the touch screen.

The device 100 also includes a power system 162 for powering the various components. The power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

The device 100 may also include one or more optical sensors 164. FIGS. 1A and 1B show an optical sensor coupled to an optical sensor controller 158 in I/O subsystem 106. The optical sensor 164 may include a charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. The optical sensor 164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 may capture still images or video. In some embodiments, an optical sensor is located on the back of the device 100, opposite the touch screen display 112 on the front of the device, so that the touch screen display may be used as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user's image may be obtained for videoconferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 may be used along with the touch screen display for both video conferencing and still and/or video image acquisition.

The device 100 may also include one or more proximity sensors 166. FIGS. 1A and 1B show a proximity sensor 166 coupled to the peripherals interface 118. Alternately, the proximity sensor 166 may be coupled to an input controller 160 in the I/O subsystem 106. The proximity sensor 166 may perform as described in U.S. patent application Ser. Nos. 11/241,839, “Proximity Detector In Handheld Device”; 11/240,788, “Proximity Detector In Handheld Device”; 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

The device 100 may also include one or more accelerometers 168. FIGS. 1A and 1B show an accelerometer 168 coupled to the peripherals interface 118. Alternately, the accelerometer 168 may be coupled to an input controller 160 in the I/O subsystem 106. The accelerometer 168 may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers.

In some embodiments, the software components stored in memory 102 may include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and applications (or set of instructions) 136.

The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

The communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by the RF circuitry 108 and/or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod (trademark of Apple, Inc.) devices.

The contact/motion module 130 may detect contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, may include determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 detects contact on a touchpad. In some embodiments, the contact/motion module 130 and the controller 160 detects contact on a click wheel.

The contact/motion module 130 may detect a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, a gesture may be detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up event.

The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.

In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic may be assigned a corresponding code. The graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

The text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

The applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:

-   -   a contacts module 137 (sometimes called an address book or         contact list);     -   a telephone module 138;     -   a video conferencing module 139;     -   an e-mail client module 140;     -   an instant messaging (IM) module 141;     -   a workout support module 142;     -   a camera module 143 for still and/or video images;     -   an image management module 144;     -   a video player module 145;     -   a music player module 146;     -   a browser module 147;     -   a calendar module 148;     -   widget modules 149, which may include weather widget 149-1,         stocks widget 149-2, calculator widget 149-3, alarm clock widget         149-4, dictionary widget 149-5, and other widgets obtained by         the user, as well as user-created widgets 149-6;     -   widget creator module 150 for making user-created widgets 149-6;     -   search module 151;     -   video and music player module 152, which merges video player         module 145 and music player module 146;     -   notes module 153;     -   map module 154; and/or     -   online video module 155.

Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contacts module 137 may be used to manage an address book or contact list, including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in the address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, the videoconferencing module 139 may be used to initiate, conduct, and terminate a video conference between a user and one or more other participants.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the e-mail client module 140 may be used to create, send, receive, and manage e-mail. In conjunction with image management module 144, the e-mail module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 may be used to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, the workout support module 142 may be used to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, the camera module 143 may be used to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 may be used to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, and speaker 111, the video player module 145 may be used to display, present or otherwise play back videos (e.g., on the touch screen or on an external, connected display via external port 124).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, the music player module 146 allows the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files. In some embodiments, the device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple, Inc.).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the browser module 147 may be used to browse the Internet, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail module 140, and browser module 147, the calendar module 148 may be used to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the search module 151 may be used to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms).

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the notes module 153 may be used to create and manage notes, to do lists, and the like.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, the online video module 155 allows the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the content of which is hereby incorporated by reference in its entirety.

Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. For example, video player module 145 may be combined with music player module 146 into a single module (e.g., video and music player module 152, FIG. 1B). In some embodiments, memory 102 may store a subset of the modules and data structures identified above. Furthermore, memory 102 may store additional modules and data structures not described above.

In some embodiments, the device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen 112 and/or a touchpad. By using a touch screen and/or a touchpad as the primary input/control device for operation of the device 100, the number of physical input/control devices (such as push buttons, dials, and the like) on the device 100 may be reduced.

The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main, home, or root menu from any user interface that may be displayed on the device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input/control device instead of a touchpad.

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen may display one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user may select one or more of the graphics by making contact or touching the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the contact may include a gesture, such as one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with the device 100. In some embodiments, inadvertent contact with a graphic may not select the graphic. For example, a swipe gesture that sweeps over an application icon may not select the corresponding application when the gesture corresponding to selection is a tap.

The device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, the menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on the device 100 (e.g., applications depicted in FIGS. 1A, 1B and 3). Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI in touch screen 112.

In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, a Subscriber Identity Module (SIM) card slot 210, a head set jack 212, and a docking/charging external port 124. The push button 206 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, the device 100 also may accept verbal input for activation or deactivation of some functions through the microphone 113.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). The device 300 typically includes one or more processing units (CPU's) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication buses 320 may include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. The device 300 includes a user interface 330 comprising a display 340, which is typically a touch screen display. The user interface 330 also may include a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355. Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 may optionally include one or more storage devices remotely located from the CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in the memory 102 of portable multifunction device 100 (FIG. 1), or a subset thereof. Furthermore, memory 370 may store additional programs, modules, and data structures not present in the memory 102 of portable multifunction device 100. For example, memory 370 of device 300 may store drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1) may not store these modules.

Each of the above identified elements in FIG. 3 may be stored in one or more of the previously mentioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 370 may store a subset of the modules and data structures identified above. Furthermore, memory 370 may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”) that may be implemented on a portable multifunction device 100.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu of applications on a portable multifunction device 100 in accordance with some embodiments. Similar user interfaces may be implemented on device 300. In some embodiments, user interface 400A includes the following elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),         such as cellular and Wi-Fi signals;     -   Time 404;     -   Bluetooth indicator 405;     -   Battery status indicator 406;     -   Tray 408 with icons for frequently used applications, such as:         -   Phone 138, which may include an indicator 414 of the number             of missed calls or voicemail messages;         -   E-mail client 140, which may include an indicator 410 of the             number of unread e-mails;         -   Browser 147; and         -   Music player 146; and     -   Icons for other applications, such as:         -   IM 141;         -   Image management 144;         -   Camera 143;         -   Video player 145;         -   Weather 149-1;         -   Stocks 149-2;         -   Workout support 142;         -   Calendar 148;         -   Calculator 149-3;         -   Alarm clock 149-4;         -   Dictionary 149-5; and         -   User-created widget 149-6.

In some embodiments, user interface 400B includes the following elements, or a subset or superset thereof:

-   -   402, 404, 405, 406, 141, 148, 144, 143, 149-3, 149-2, 149-1,         149-4, 410, 414, 138, 140, and 147, as described above;     -   Map 154;     -   Notes 153;     -   Settings 412, which provides access to settings for the device         100 and its various applications 136, as described further         below;     -   Video and music player module 152, also referred to as iPod         (trademark of Apple, Inc.) module 152; and     -   Online video module 155, also referred to as YouTube (trademark         of Google, Inc.) module 155.

FIG. 4C illustrates an exemplary user interface on a multifunction device with a separate display (e.g., 450) and touch-sensitive surface (e.g., 451). Although many of the examples which follow will be given with reference to a touch screen display (e.g., where the touch sensitive surface and the display are combined, as shown in device 100 in FIGS. 4A-4B), in some embodiments the display and the touch-sensitive surface are separate, as shown in FIG. 4C. In some embodiments the touch sensitive surface (e.g., 451 in FIG. 4C) has a primary axis (e.g., 452 in FIG. 4C) that corresponds to a primary axis (e.g., 453 in FIG. 4C) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4C) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4C 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462 in directions 464 and 466, respectively) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4C) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4C) of the multifunction device when the touch-sensitive surface and the display are separate. It should be understood that similar methods may be used for other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or stylus input). For example, a swipe gesture may be replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture may be replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice may be used simultaneously, or a mouse and finger contacts may be used simultaneously.

Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on a multifunction device with a display and a touch-sensitive surface, such as device 300 or portable multifunction device 100.

FIGS. 5A-5P illustrate exemplary user interfaces for managing user interface content and user interface elements with alignment guides configured for adaptive snap-to behavior in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 6A-6C.

UI 500A (FIG. 5A) depicts an exemplary user interface UI 500A displayed on device 100. In this example, the user interface includes an electronic canvas 500 with user interface elements displayed as moveable objects, i.e., circle 501, rectangle 502, and diamond 503. Near a corner of rectangle 502, a user has made, and the device has detected, a single finger contact 505 on the touch screen 112.

UI 500A also depicts that device 100 detects the initiation of the first portion of first user gesture 507-1 on the touch screen 112.

UI 500B (FIG. 5B) illustrates that, after detecting the first portion of the first user gesture 507-1 in UI 500A, the device displays some possible alignment guides in conjunction with the displayed objects circle 501, rectangle 502, and diamond 503 (i.e., attachment handles 501-a and 501-b with respect to circle 501; attachment handles 502-a and 502-b, and extended alignment guide 502-c with respect to rectangle 502; and attachment handles 503-a and 503-b, and extended alignment guides 503-c, 503-d, and 503-e with respect to diamond 503). Alignment guides 503-c, 503-d, and 503-e are configured with respective gravity variables configured to vary the attraction strength. In these exemplary user interface figures, the gravity variables for alignment guides 503-c, 503-d, and 503-e are set to 100%, 80%, and 100%, respectively. For purposes of illustration, these gravity variable values are displayed in conjunction with the reference numerals for alignment guides 503-c, 503-d, and 503-e.

UI 500B also illustrates that in response to detecting the first portion of the first user gesture 507-1 in UI 500A, the device initiated movement of rectangle 502 within the user interface, i.e., on the electronic canvas 500.

UI 500C (FIG. 5C) depicts that device 100 detects the continuation of the first portion of first user gesture 507-1 on the touch screen 112. UI 500C also depicts that rectangle 502 has moved from its original position on electronic canvas 500 in accordance with first portion of first user gesture 507-1. Rectangle 502 is now near extended alignment guide 503-c.

For illustrative purposes, magnified region 508 of the area between diamond 503 and rectangle 502 is depicted. Magnified region 508 includes images of visibly displayed extended alignment guide 502-c and extended alignment guide 503-c, as well as line 509 associated with extended alignment guide 503-c. Line 509 represents a predefined distance threshold 509-d associated with diamond 503's extended alignment guide 503-c. Rectangle 502's position, as represented by extended alignment guide 502-c in magnified region 508, is closer to extended alignment guide 503-c than the line 509, which represents the predefined distance threshold 509-d. (Line 509 is not displayed in some embodiments.)

UI 500D (FIG. 5D) depicts that rectangle 502 was snapped to extended alignment guide 503-c, an extended edge-alignment guide. Thus, extended alignment guide 503-c, an extended edge-alignment guide for diamond 503, and extended alignment guide 502-c, an extended edge-alignment guide for rectangle 502, are aligned.

UI 500E (FIG. 5E) depicts that the device 100 detects second portion of first user gesture 507-2, which is different than first portion of first user gesture 507-1 because second portion of first user gesture 507-2 is in a different direction, viz., second portion of first user gesture 507-2 is in a direction away from extended alignment guide 503-c, while first portion of first user gesture 507-1 was towards extended alignment guide 503-c.

Note that, in some embodiments, second portion of first user gesture 507-2 is detected on the touch screen 112 without detecting liftoff from touch screen 112 after the first portion of first user gesture 507-1 is completed, e.g., if first portion of first user gesture 507-1 is performed with a user finger contact on touch screen 112, second portion of first user gesture 507-2 is performed without lifting the user's finger after completing first portion of first user gesture 507-1.

UI 500E also depicts that after detecting second portion of first user gesture 507-2, the gravity variable for extended alignment guide 503-c is adjusted from 100% to 50%.

UI 500E-UI 500G (FIGS. 5F-5G) depict that the device 100 detects third portion of first user gesture 507-3, which approaches extended alignment guide 503-c, the extended edge-alignment guide for diamond 503 that rectangle 502 was snapped to during first portion of first user gesture 507-1.

Note that rectangle 502 does not snap to diamond 503's extended alignment guide 503-c, despite the fact that rectangle 502 is near extended alignment guide 503-c.

Also note that, in some embodiments, third portion of first user gesture 507-3 is detected on the touch screen 112 without detecting liftoff from touch screen 112 after the second portion of first user gesture 507-2 is completed, e.g., if second portion of first user gesture 507-2 is performed with a user finger contact on touch screen 112, third portion of first user gesture 507-3 is performed without lifting the user's finger after completing second portion of first user gesture 507-2. For example, the user contacts touch screen 112 above rectangle 502 and begins to move it towards the alignment guides associated with diamond 503 (UI 500A, UI 500B first portion of first gesture 507-1). After movement of rectangle 502 begins, the device “snaps” rectangle 502 to an alignment guide (UI 500D) when appropriate, as discussed further below. However, if this automatic snap is not what the user desired, the user moves rectangle 502 away from the alignment guide snapped to after the first portion of the first gesture (UI 500E). This movement away from the alignment guide snapped to after the first portion of the first gesture is the second portion of the first gesture (UI 500E, second portion of first gesture 507-2). After the second portion of the first gesture, the device decreases the strength of the alignment guide snapped to (UI 500E, extended alignment guide 503-c) after the first portion of the first gesture to insure that rectangle 502 does not snap as easily to the undesired alignment guide during the third portion of the first gesture (UI 500F 507-3).

UI 500H (FIG. 5H) depicts that rectangle 502 snapped to extended middle alignment guide 503-d of diamond 503.

Though not illustrated directly in UI 500H, single finger contact 505 is removed from touch screen 112, and therefore, termination of first user gesture 507 is detected.

UI 500I (FIG. 5I) depicts that, in response to detecting termination of first user gesture 507, the alignment guides displayed in conjunction with displayed objects circle 501, rectangle 502, and diamond 503 are removed.

UI 500J (FIG. 5J) illustrates a user has made, and the device has detected, a single finger contact 510 on rectangle 502 on the touch screen 112. In response to detecting single finger contact 510 on rectangle 502, the device has displayed some of the alignment guides possible to display in conjunction with the displayed objects circle 501, rectangle 502, and diamond 503 (i.e., attachment handles 501-a and 501-b with respect to circle 501; attachment handles 502-a and 502-b, and extended alignment guide 502-c with respect to rectangle 502; and attachment handles 503-a and 503-b, and extended alignment guides 503-c, 503-d, and 503-e with respect to diamond 503).

UI 500J also depicts that device 100 detects the initiation of the first portion of second user gesture 512-1 on the touch screen 112.

UI 500J also illustrates, that the adjusted value of the gravity variable associated with the extended alignment guide 503-c was maintained at 50% after termination of first user gesture 507.

UI 500K (FIG. 5K) illustrates that in response to detecting the first portion of second user gesture 512-1 in UI 500J, the device initiates movement of rectangle 502 within the user interface on electronic canvas 500, and rectangle 502 has moved on electronic canvas 500 in accordance with first portion of second user gesture 512-1.

UI 500L (FIG. 5L) depicts that device 100 detects the initiation of second portion of second user gesture 512-2 on touch screen 112.

UI 500M (FIG. 5M) depicts that device 100 detects the continuation of second portion of second user gesture 512-2 on the touch screen 112. UI 500M also depicts that rectangle 502 has moved in accordance with second portion of second user gesture 512-2. Rectangle 502 is again near extended alignment guide 503-c associated with diamond 503, and the gravity variable associated with extended alignment guide 503-c is still set at 50% during second user gesture 512 after it was adjusted from 100% during first user gesture 507.

UI 500N (FIG. 5N) depicts that device 100 detects further continuation of second portion of second user gesture 512-2 on the touch screen 112, which results in extended alignment guide 502-c of rectangle 502 passing extended alignment guides 503-c and 503-d associated with diamond 503, despite the fact that rectangle 502 passed by extended alignment guides 503-c and 503-d.

UI 500O (FIG. 5O) depicts that in response to second portion of second user gesture 512-2, the device snaps rectangle 502 to extended alignment guide 503-e associated with diamond 503. Extended alignment guide 503-e, whose gravity variable is set at 100%, is currently the highest gravity value for an alignment guide associated with diamond 503.

Though not illustrated directly in UI 500O, single finger contact 510 is removed from touch screen 112, and therefore, termination of second user gesture 512 is detected.

UI 500P (FIG. 5P) depicts that, in response to detecting termination of second user gesture 512, the alignment guides visibly displayed in conjunction with displayed objects circle 501, rectangle 502, and diamond 503 are removed.

Though the exemplary user interfaces illustrated in UI 500A-UI 500P illustrate alignment guides displayed in conjunction with displayed user interface objects, alignment guides compatible with the methods disclosed herein may be independent of any displayed object, e.g., respective alignment guides that are independent of any displayed object can be used to facilitate user gestures for movement or resizing of user interface elements, and the attraction strength of individual alignment guides can be adjusted via user gestures following an unintended snap of a user interface element to an alignment guide.

In some embodiments, the following method is used to adjust attraction strength of individual alignment guides:

-   -   After detecting initiation of a user interface element resize or         move gesture in a first direction, identify potential alignment         guides the resize or move gesture might intersect.     -   During the user interface element resize or move gesture:         -   Determine respective match-priority values for respective             identified potential alignment guides, using at least:             -   distance between respective identified potential                 alignment guides and the user interface element being                 moved, and             -   gravity values associated with respective identified                 potential alignment guides.         -   Identify the largest respective match-priority value             associated with an identified potential alignment guide.         -   Determine the distance between the user interface element             and the potential alignment guide associated with the             largest respective match-priority value.         -   When the largest respective match-priority value is larger             than a predefined value, and the distance between the             alignment guide associated with the largest respective             match-priority value and the user interface element is less             than the predefined distance threshold, (e.g., 5 pixels, 10             pixels, 15 pixels, 20 pixels, 30 pixels, or any suitable             distance, and may be measured relative to the display itself             or relative to an electronic canvas displayed with a             magnification factor ranging from no magnification to a             high-magnification factor), snap the user interface element             being moved to the alignment guide associated with the             largest respective match-priority value.     -   After a snap of the user interface element to an alignment guide         occurs, and the user interface element resize or move gesture         has not terminated:         -   When the user interface element resize or move gesture             continues in the first direction, detach the user interface             element from the alignment guide that was snapped to.         -   When the user interface element resize or move gesture             continues in a direction away from the first direction,             adjust the gravity value associated with the alignment guide             that was snapped to, i.e., apply a penalty to that alignment             guide's gravity value.         -   Continue determining respective match-priority values for             respective identified potential alignment guides.

Gravity values for alignment guides may be assigned by any suitable method, including without limitation, associating a percentage with an alignment guide, e.g., 1%, 25%, 100%, 200%, 500%, or any suitable value.

Determination of match-priority values for respective alignment guides may be determined by any suitable method that involves respective distances and respective gravity values, including without limitation, either of the exemplary formulae: Match-Priority_((alignment guide i))Gravity Value_((alignment guide i))/distance_((alignment guide i)) ²  Equation 1 Match-Priority_((alignment guide i))=Gravity Value_((alignment guide i))*MAXIMUM(0,10−distance_((alignment guide i)))  Equation 2

For example, if there are two potential alignment guides near a user interface element being moved, where the user interface element is 13 pixels from alignment guide 1 and 8 pixels from alignment guide 2, and the gravity values are set at 100% and 84% for alignment guides 1 and 2, respectively. Equation 1 would provide the following results:

alignment guide 1 match priority value: 0.0059=1.0/13²

alignment guide 2 match priority value: 0.0123=0.84/8²

Equation 2 would provide the following results:

alignment guide 1 match priority value: 0=1.0*MAXIMUM (0, (10-13))

alignment guide 2 match priority value: 1.68=0.84*MAXIMUM (0, (10-8))

Though these exemplary equations provide different numeric results, the values calculated for respective match-priority values can be used to determine when a respective match-priority value is larger than a predefined value. For example, the results generated with Equation 1 may be compared to a predefined value of 0.01 to determine whether to snap the user interface element being moved to the alignment guide associated with the largest respective match-priority value, i.e., snap the user interface element to alignment guide 2 since the match-priority value is greater than 0.01, assuming that other conditions are met, e.g., being close enough to alignment guide 2.

Similarly, the results generated with Equation 2 may be compared to a predefined value, such as 1.5, to determine whether to snap the user interface element being moved to the alignment guide associated with the largest respective match-priority value, i.e., snap the user interface element to alignment guide 2 since the match-priority value is greater than 1.5, assuming that other conditions are met, e.g., being close enough to alignment guide 2.

FIGS. 6A-6B are flow diagrams illustrating a method 600 of managing user interface content and user interface elements with alignment guides configured for adaptive snap-to behavior in accordance with some embodiments. The method 600 is performed at a multifunction device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 600 may be combined and/or the order of some operations may be changed.

As described below, the method 600 provides an intuitive way to manipulate user interface objects. The method reduces the cognitive burden on a user when manipulating user interface objects, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manipulate user interface objects faster and more efficiently conserves power and increases the time between battery charges.

The method 600 is performed at a computing device with a display and one or more user input devices adapted to detect user gestures (e.g., FIG. 5A portable multifunction device 100, FIG. 3 device 300). The device displays a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein: respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold (e.g., FIG. 5C, predefined distance threshold 509-d, which may be 5 pixels, 10 pixels, 15 pixels, 20 pixels, 30 pixels, or any suitable distance, and may be measured relative to the display itself or relative to an electronic canvas displayed with a magnification factor ranging from no magnification to a high-magnification factor) to the respective alignment guide, and respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved (e.g., FIG. 5B electronic canvas 500, which displays some possible alignment guides in conjunction with the displayed objects circle 501, rectangle 502, and diamond 503, i.e., attachment handles 501-a and 501-b with respect to circle 501; attachment handles 502-a and 502-b, and extended alignment guide 502-c with respect to rectangle 502; and attachment handles 503-a and 503-b, and extended alignment guides 503-c, 503-d, and 503-e with respect to diamond 503, where at least extended alignment guides 503-c, 503-d, and 503-e are configured to attract the user interface element being moved, namely rectangle 502. Respective alignment guides 503-c, 503-d, and 503-e are associated with respective gravity variables configured to vary the attraction strength. For purposes of illustration, the gravity variables for alignment guides 503-c, 503-d, and 503-e are set to 100%, 80%, and 100%, respectively.) (602).

In some embodiments, user interface elements are configured to be attracted to alignment guides, rather than alignment guides being configured to attract user interface elements. In some embodiments, all respective alignment guides are configured to attract the user interface element being manipulated during a gesture, while in alternate embodiments, one or more of the alignment guides in the plurality of alignment guides is configured to attract the user interface element being manipulated during a gesture.

In some embodiments, the user interface implements a physics-based model of attraction between the alignment guides and user interface elements being moved to simulate gravitational attraction. Accordingly, increasing or decreasing a gravity variable for a respective alignment guide strengthens or weakens, respectively, the ease with which a user interface element snaps to a respective alignment guide.

In some embodiments, at least some of the plurality of alignment guides is visibly displayed (e.g., FIG. 5B extended alignment guides 503-c, 503-d, and 503-e are visibly displayed) (604).

In some embodiments, the plurality of alignment guides includes one or more alignment guide types selected from the group consisting of edge-to-middle-slide alignment guides, edge-to-edge alignment guides, and middle-to-middle alignment guides, electronic canvas middle alignment guides, electronic canvas edge alignment guides, electronic canvas top, bottom, left, and right margin alignment guides, the location of an arbitrarily defined split of an electronic canvas, e.g. an electronic canvas split into three regions, alignment guides defined within a document theme or master template, and user-defined alignment guides (e.g., FIG. 5B extended middle alignment guide 503-d and extended edge alignment guide 503-c)(606)

In some embodiments, the default value of the gravity variable varies based on alignment guide type, i.e., different types of alignment guides have different default gravity variable values (e.g., FIG. 5B extended middle alignment guide 503-d, which is set at 80%, while extended edge alignment guide 503-c is set at 100%) (608).

In some embodiments, the one or more user interface elements are displayed on an electronic canvas (e.g., FIG. 5C, electronic canvas 500, displaying user interface elements as moveable objects, i.e., circle 501, rectangle 502, and diamond 503) (610).

In some embodiments, the display and at least one of the one or more user input devices comprise a touch-screen display (e.g., FIG. 5A includes a touch screen 112) (612).

The device detects (614) a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface (e.g., FIG. 5A, device 100 detects the initiation of the first portion of first user gesture 507-1 on the touch screen 112).

In response to detecting the first portion of the first user gesture, the device initiates movement (616) of the user interface element within the user interface (e.g., in UI 500A, in response to detecting the first portion of the first user gesture 507-1, in UI 500B and UI 500C the device 100 moves rectangle 502 within the user interface, i.e., on the electronic canvas 500).

After movement of the user interface element is initiated, the device snaps (618) or moves the user interface element to a first alignment guide (e.g., FIG. 5D, rectangle 502 was snapped to extended alignment guide 503-c, an extended edge-alignment guide). For example, this may occur when the user interface element is closer to the first alignment guide than the first predetermined distance threshold and/or the gravity variable associated with the first alignment guide exceeds a value corresponding to a gravitational attraction threshold, e.g. 70%, 75%, 80%, 85%, 90%, or any suitable value.

In some embodiments, moving or snapping a user interface element to an alignment guide includes automatic movement of the user interface element to an alignment guide irrespective of whether the user gesture includes a specific movement that moves the user interface element to the specific alignment guide snapped to, i.e., once a snap movement of a user interface element begins, the user interface element is automatically moved to a specific alignment guide independent of any further movement of the user gesture.

After snapping the user interface element to the first alignment guide, the device detects (620) a second portion of the first user gesture that is different than the first portion of the first user gesture, e.g., moving away from the first alignment guide (e.g., FIG. 5E illustrates that device 100 detects second portion of first user gesture 507-2, which is different than first portion of first user gesture 507-1 because second portion of first user gesture 507-2 is in a different direction than first portion of first user gesture 507-1).

In some embodiments, the second portion of the first user gesture is a continuation of the user gesture where the user moves away from an alignment guide that the user interface element snapped to.

In response to detecting the second portion of the first user gesture, the device moves the user interface element away from the first alignment guide, and the device adjusts, e.g., decreases, the gravity variable associated with the first alignment guide (622) (e.g., FIG. 5E, after detecting second portion of first user gesture 507-2, the device 100 moves rectangle 502 away from extended alignment guide 503-c, and the gravity variable associated with extended alignment guide 503-c is adjusted from 100% to 50%).

After adjusting the gravity variable associated with the first alignment guide, the device detects a third portion of the first user gesture (e.g., FIGS. 5F and 5G, device 100 detects third portion of first user gesture 507-3), and in response to detecting the third portion of the first user gesture, the device snaps the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide (624) (e.g., FIG. 5H, rectangle 502 is snapped to extended alignment guide 503-d, and the gravity variable associated with extended alignment guide 503-c is 50% while the gravity variable associated with extended alignment guide 503-d is 80%).

In some embodiments, snapping to the second alignment guide rather than the first alignment guide occurs irrespective of whether the user interface element is closer than the first predefined distance threshold to the first alignment guide because the gravity variable associated with the second alignment guide is stronger than the gravity variable associated with the first alignment guide (e.g., as shown in FIG. 5H, rectangle 502 is snapped to extended alignment guide 503-d, where in FIG. 5G, the gravity variable associated with extended alignment guide 503-c is 50%, the gravity variable associated with extended alignment guide 503-d is 80%, rectangle 502-c is closer to extended alignment guide 503-c than extended alignment guide 503-d, and rectangle 502-c is closer to extended alignment guide 503-c than the predefined distance threshold 509-d depicted in FIG. 5C, which for purposes of clarity, is not illustrated in FIG. 5G).

In some embodiments, the device calculates respective alignment guide match-priority values for at least two alignment guides that are in proximity to the user interface element being moved, wherein respective alignment guide match-priority values are calculated using at least the distance between the respective alignment guide and the user interface element being moved, and the value of the gravity variable for the respective alignment guide (626) (not depicted in figures). In some embodiments, the user interface element is moved to the second alignment guide when the calculated match-priority value for the second alignment guide is greater than the calculated match-priority value for the first alignment guide (628) (not depicted in figures).

In some embodiments, the device detects a termination of the first user gesture, e.g., the user lifting off a finger from a touch screen display, thereby ending the first user gesture (630) (e.g., FIG. 5H, single finger contact 505 is removed from touch screen 112, and therefore, the device detects termination of first user gesture 507).

In some embodiments, in response to detecting the termination of the first user gesture, the device resets the gravity variable associated with the first alignment guide to a default value (632) (not depicted in figures). In alternative embodiments, in response to detecting the termination of the first user gesture, the device maintains the adjusted value of the gravity variable associated with the first alignment guide (634) (e.g., FIG. 5J the adjusted value of the gravity variable associated with the extended alignment guide 503-c was maintained at 50% after termination of first user gesture 507).

In some embodiments, the adjusted value of the gravity variable associated with the first alignment guide is maintained for a succession of user gestures for moving the user interface element within the user interface (636) (e.g., FIG. 5M, the gravity variable associated with extended alignment guide 503-c is still set at 50% during second user gesture 512, after it was adjusted from 100% during first user gesture 507).

In some embodiments, the device incrementally adjusts the gravity variable associated with the first alignment guide upon detecting termination of respective user gestures in the succession of user gestures (638), i.e., after a user has performed a gesture that results in the gravity variable being adjusted, the gravity variable will be adjusted an incremental portion at a time back towards the default value (not depicted in figures). For example, after the gravity variable associated with the first alignment guide is adjusted from a value of 100%—a default setting—to a value of 25%, the user performs three more user gestures in succession. As the user performs the first user gesture in the succession of three user gestures, the gravity variable associated with the first alignment guide is adjusted from the value of 25% to a value of 50%. When the user performs the second user gesture in the succession of three user gestures, the gravity variable associated with the first alignment guide is adjusted from the value of 50% to a value of 75%. When the user performs the third user gesture in the succession of three user gestures, the gravity variable associated with the first alignment guide is adjusted from the value of 75% to a value of 100%. Though this example uses a simple linear function to adjust the gravity variable associated with the first alignment guide back to its default value, any suitable mathematical function to adjust the gravity variable value back to a default value over a succession of user gestures may be used.

FIG. 6C is a flow diagram illustrating a method 650 of managing user interface content and user interface elements with alignment guides configured for adaptive snap-to behavior in accordance with some embodiments. The method 650 is performed at a multifunction device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface.

Some operations in method 650 may be combined and/or the order of some operations may be changed. Additionally, operations in method 650 may be combined with some operations in method 600 and/or the order of some combined operations may be changed.

As described below, the method 650 provides an intuitive way to manipulate user interface objects. The method reduces the cognitive burden on a user when manipulating user interface objects, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manipulate user interface objects faster and more efficiently conserves power and increases the time between battery charges.

The method 650 is performed at a computing device with a display and one or more user input devices adapted to detect user gestures (e.g., FIG. 5A portable multifunction device 100, FIG. 3 device 300). The device displays a user interface including at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved (e.g., FIG. 5B electronic canvas 500, which displays some possible alignment guides in conjunction with the displayed objects circle 501, rectangle 502, and diamond 503, i.e., attachment handles 501-a and 501-b with respect to circle 501; attachment handles 502-a and 502-b, and extended alignment guide 502-c with respect to rectangle 502; and attachment handles 503-a and 503-b, and extended alignment guides 503-c, 503-d, and 503-e with respect to diamond 503, where at least extended alignment guides 503-c, 503-d, and 503-e are configured to attract the user interface element being moved, namely rectangle 502. Respective alignment guides 503-c, 503-d, and 503-e are associated with respective gravity variables are configured to vary the attraction strength. For purposes of illustration, the gravity variables for alignment guides 503-c, 503-d, and 503-e are set to 100%, 80%, and 100%, respectively.) (652).

The device detects (654) a first portion of a user gesture, the user gesture corresponding to a gesture to move the user interface element within the user interface (e.g., FIG. 5A, device 100 detects the initiation of the first portion of first user gesture 507-1 on the touch screen 112).

In response to detecting the first portion of the user gesture, the device moves (656) the user interface element within the user interface (e.g., in FIG. 5A, in response to detecting the first portion of the first user gesture 507-1, in FIG. 5B and FIG. 5C the device 100 moves rectangle 502 within the user interface, i.e., on the electronic canvas 500).

While the user interface element is moving within the user interface, the device determines respective locations within the user interface of the user interface element (658) (e.g., in FIG. 5C, while the device 100 moves rectangle 502 within the user interface, i.e., on the electronic canvas 500, the device 100 determines respective locations of rectangle 502 within the user interface).

When the user interface element is at respective locations of the user interface: the device determines respective match priority values for a plurality of alignment guides, wherein respective match priority values are based at least on respective gravity variables and a current location of the user interface element (660) (e.g., not explicitly depicted, but in FIG. 5B and FIG. 5C, while the device 100 moves rectangle 502 within the user interface and rectangle 502 is at respective locations on electronic canvas 500, the device determines respective match priority values for the current respective location of rectangle 502 and extended alignment guides 503-c, 503-d, and 503-e); and the device compares a match priority value associated with a first alignment guide in the plurality of alignment guides with a match priority value associated with a second alignment guide in the plurality of alignment guides (662) (e.g., not explicitly depicted, but in FIG. 5C, the device compares the match priority value associated with extended alignment guide 503-c with the match priority value associated with extended alignment guide 503-d).

The device snaps (664) the user interface element to an alignment guide associated with a greatest determined match priority value (e.g., in FIG. 5D, the device 100 snaps rectangle 502 to extended alignment guide 503-c, which has a greater determined match priority than extended alignment guide 503-d, at least because the gravity variable value for extended alignment guide 503-c is set to 100% while the gravity variable value for extended alignment guide 503-d is set to 80%).

In some embodiments, after snapping the user interface element to the first alignment guide, the device detects a second portion of the user gesture, the second portion of the user gesture corresponding to a gesture to move the user interface element within the user interface away from the first alignment guide (e.g., FIG. 5E, second portion of first user gesture 507-2); after detecting the second portion of the user gesture, the device moves the user interface element away from the first alignment guide (e.g., FIG. 5F, after detecting second portion of first user gesture 507-2, the device 100 moves rectangle 502 away from extended alignment guide 503-c); and the device adjusts (e.g., decreases) the gravity variable associated with the first alignment guide (e.g., FIG. 5F, the gravity variable associated with extended alignment guide 503-c is adjusted from 100% to 50%) (666).

The steps in the information processing methods described above may be implemented by running one or more functional modules in information processing apparatus such as general purpose processors or application specific chips, such as ASICs, FPGAs, PLDs, or other appropriate devices. These modules, combinations of these modules, and/or their combination with general hardware (e.g., as described above with respect to FIGS. 1A, 1B and 3) are all included within the scope of protection of the invention.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. 

1. A method, comprising: at a computing device with a display and one or more user input devices adapted to detect user gestures: displaying a user interface including: at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein: respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved; detecting a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, initiating movement of the user interface element within the user interface; after movement of the user interface element is initiated, snapping the user interface element to a first alignment guide; after snapping the user interface element to the first alignment guide, detecting a second portion of the first user gesture that is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: moving the user interface element away from the first alignment guide, and, adjusting the gravity variable associated with the first alignment guide; after adjusting the gravity variable associated with the first alignment guide: detecting a third portion of the first user gesture; in response to detecting the third portion of the first user gesture, snapping the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide; detecting a termination of the first user gesture; in response to detecting the termination of the first user gesture: maintaining the adjusted value of the gravity variable associated with the first alignment guide, wherein the adjusted value of the gravity variable associated with the first alignment guide is maintained for a succession of user gestures for moving the user interface element within the user interface; and incrementally adjusting the gravity variable associated with the first alignment guide upon detecting termination of respective user gestures in the succession of user gestures.
 2. The method of claim 1, further comprising: calculating respective alignment guide match-priority values for at least two alignment guides that are in proximity to the user interface element being moved, wherein respective alignment guide match-priority values are calculated using at least: a distance between the respective alignment guide and the user interface element being moved, and, the value of the gravity variable for the respective alignment guide.
 3. The method of claim 2, wherein the user interface element is moved to the second alignment guide when the calculated match-priority value for the second alignment guide is greater than the calculated match-priority value for the first alignment guide.
 4. The method of claim 1, wherein the plurality of alignment guides is visibly displayed.
 5. The method of claim 1, wherein the plurality of alignment guides includes one or more alignment guide types selected from the group consisting of edge-to-middle alignment guides, edge-to-edge alignment guides, and middle-to-middle alignment guides.
 6. The method of claim 5, wherein the default value of the gravity variable varies based on alignment guide type.
 7. The method of claim 1, wherein the one or more user interface elements are displayed on an electronic canvas.
 8. The method of claim 1, wherein the display and at least one of the one or more user input devices comprise a touch-screen display.
 9. A computing device, comprising: a display; one or more processors; one or more user input devices adapted to detect user gestures; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a user interface including: at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein: respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved; detecting a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, initiating movement of the user interface element within the user interface; after movement of the user interface element is initiated, snapping the user interface element to a first alignment guide; after snapping the user interface element to the first alignment guide, detecting a second portion of the first user gesture that is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: moving the user interface element away from the first alignment guide, and, adjusting the gravity variable associated with the first alignment guide; after adjusting the gravity variable associated with the first alignment guide: detecting a third portion of the first user gesture; in response to detecting the third portion of the first user gesture, snapping the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide, detecting a termination of the first user gesture; in response to detecting the termination of the first user gesture: maintaining the adjusted value of the gravity variable associated with the first alignment guide, wherein the adjusted value of the gravity variable associated with the first alignment guide is maintained for a succession of user gestures for moving the user interface element within the user interface; and incrementally adjusting the gravity variable associated with the first alignment guide upon detecting termination of respective user gestures in the succession of user gestures.
 10. The computing device of claim 9, wherein the plurality of alignment guides includes one or more alignment guide types selected from the group consisting of edge-to-middle alignment guides, edge-to-edge alignment guides, and middle-to-middle alignment guides.
 11. The computing device of claim 10, wherein the default value of the gravity variable varies based on alignment guide type.
 12. The computing device of claim 9, wherein the display and at least one of the one or more user input devices comprise a touch-screen display.
 13. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computing device with a display and one or more user input devices adapted to detect user gestures, cause the device to: Display a user interface including: at least one user interface element configured to be moved within the user interface in response to user gestures, and a plurality of alignment guides, wherein: respective alignment guides in the plurality of alignment guides are configured to attract the user interface element being moved when the user interface element is closer than a first predefined distance threshold to the respective alignment guide, and, respective alignment guides in the plurality of alignment guides are associated with respective gravity variables configured to vary the attraction strength between the alignment guide and the user interface element being moved; detect a first portion of a first user gesture, the first user gesture corresponding to a gesture to move the user interface element within the user interface; in response to detecting the first portion of the first user gesture, initiate movement of the user interface element within the user interface; after movement of the user interface element is initiated, snapthe user interface element to a first alignment guide; after snapping the user interface element to the first alignment guide, detect a second portion of the first user gesture that is different than the first portion of the first user gesture; in response to detecting the second portion of the first user gesture: move the user interface element away from the first alignment guide, and, adjust the gravity variable associated with the first alignment guide; after adjusting the gravity variable associated with the first alignment guide: detect a third portion of the first user gesture; in response to detecting the third portion of the first user gesture, snap the user interface element to a second alignment guide in the plurality of alignment guides when a gravity variable associated with the second alignment guide is greater than the gravity variable associated with the first alignment guide; after snapping the user interface element to the second alignment guide, detect a termination of the first user gesture; in response to detecting the termination of the first user gesture: maintain the adjusted value of the gravity variable associated with the first alignment guide, wherein the adjusted value of the gravity variable associated with the first alignment guide is maintained for a succession of user gestures for moving the user interface element within the user interface; and incrementally adjust the gravity variable associated with the first alignment guide upon detecting termination of respective user gestures in the succession of user gestures. 